
This resource address can be used to update the properties for the specified user.
| URL Parameters | |
|---|---|
| format | The format of the posted data. Can be either
json (default) or xml. This value overrides the Accept header if
both are present. |
| Response Headers | |
|---|---|
| Content-type | The MIME type of the data in the response
body. Depending upon the value of the format parameter or Accept header, either
application/xml or application/json. |
Upon success, MarkLogic Server returns status code 204 (No Content). If the payload is malformed or the database does not exist, a status code of 400 (Bad Request) is returned. A status code of 401 (Unauthorized) is returned if the user does not have the necessary privileges.
security and
manage-admin roles. user-name is specified, password must also be specified. Note:
The properties described here are for XML payloads. In general they are the same for JSON,
with the exception that, in JSON, roles, external-names,
permissions, and collections are expressed in singular form. For
example, in JSON, permissions is instead permission and the format
is: "permission":[{"role-name":"name", "capability":"cap"}].
user-namedescriptionpasswordexternal-namesThis is a complex structure with the following children:
external-namerolesThis is a complex structure with the following children:
rolepermissionsThis is a complex structure with the following children:
permissionThis is a complex structure with the following children:
role-namecapabilitycollectionsThis is a complex structure with the following children:
collection
curl -X PUT --anyauth -u admin:admin -H "Content-Type:application/json" \
-d '{"description":"joe cool"}' http://localhost:8002/manage/v2/users/Joe/properties
==> Changes the description for the user, "joe," to "joe cool."
Stack Overflow: Get the most useful answers to questions from the MarkLogic community, or ask your own question.